From c8140262164d2b8dfe23a39bf54340a242c0f41b Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Wed, 1 Oct 2025 20:18:44 +0000 Subject: [PATCH] Added a comment --- .../comment_8_b545d29519e57fbc2d563ce6d9aafdb7._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/import_tree_from_rsync_special_remote/comment_8_b545d29519e57fbc2d563ce6d9aafdb7._comment diff --git a/doc/todo/import_tree_from_rsync_special_remote/comment_8_b545d29519e57fbc2d563ce6d9aafdb7._comment b/doc/todo/import_tree_from_rsync_special_remote/comment_8_b545d29519e57fbc2d563ce6d9aafdb7._comment new file mode 100644 index 0000000000..268f8cab57 --- /dev/null +++ b/doc/todo/import_tree_from_rsync_special_remote/comment_8_b545d29519e57fbc2d563ce6d9aafdb7._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 8" + date="2025-10-01T20:18:43Z" + content=""" +FTR: apparently sshfs is based on sftp and that one provides no means to access original inode. Not yet sure on what then it could say about stability of inode across remounts/as whether sensible to rely on it. Useful ref with pointers [sshfs/issues/109#issuecomment-2755824670](https://github.com/libfuse/sshfs/issues/109#issuecomment-2755824670) +"""]] -- 2.30.2